Merged
Conversation
3489be2 to
ea0a8e0
Compare
alexvuong
reviewed
Feb 25, 2026
| | shopper-login | 1.46.0 | | ||
| | campaigns | 1.0.40 | | ||
| | catalogs | 1.0.46 | | ||
| | cors-preferences | 1.1.0 | |
Contributor
There was a problem hiding this comment.
Should this be cors-preferences-oas-v1=1.0.9 instead? We probably can add some context here to know where this package comes from since it is not existing in previous version. E.g
Cors-preferences-oas is now renamed to cors-oas, but the isomorphic still works with old namespace
Collaborator
Author
There was a problem hiding this comment.
No, it should just be the API name, the commerce SDK has also been updated to work with the old names so I think we're okay on that front
alexvuong
approved these changes
Feb 25, 2026
vcua-mobify
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the APIs in alignment with ECOM v26.3, and prepares the release for March 3rd, when we will create a github release and release to NPM.
Some things to note is the following APIs have been renamed:
Some generation scripts have been updated to account for this change, but no class names have been changed
How to test
Easiest way I've found to test is to check the diff between the generated SDKs:
git checkout main && git pullnpm install --legacy-peer-deps && npm run buildgit checkout release/20260223.gitignoreand removerenderedTemplatesgit add . && git commit -m ""npm run build